-- card: 51048 from stack: in
-- bmap block id: 0
-- flags: 0000
-- background id: 50584
-- name: Naming Facilities E/4
----- HyperTalk script -----
on openCard
  beenHereFlag 2,1
  -- first param is item #, second is line # (of global)
  pass openCard
end openCard


-- part 2 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=493 top=319 right=341 bottom=512
-- title width / last selected line: 0
-- icon id / first selected line: 1400 / 1400
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Next
----- HyperTalk script -----
on mouseUp

end mouseUp


-- part 3 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=478 top=319 right=341 bottom=498
-- title width / last selected line: 0
-- icon id / first selected line: 1401 / 1401
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Prev
----- HyperTalk script -----
on mouseUp

end mouseUp



-- part contents for background part 6
----- text -----
51048

-- part contents for background part 24
----- text -----
In other types of networks, the network addresses are an integral part of 
the network interface card. These addresses are assigned at the time of manufacture or at the time of installation by the end user.

Also, in other LANs a separate database and software module is required. The network administrator must add every “user” and “resource” and record their attributes (like security level, etc.).  All modules of the network can then access this naming service when required.


-- part contents for background part 5
----- text -----
Example 2:  Naming Services in Other LANs

-- part contents for background part 3
----- text -----
Naming Facilities